View AT26DF161-SU_1785640.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

features ? single 2.7v - 3.6v supply ? serial peripheral inte rface (spi) compatible ? supports spi modes 0 and 3 ? 66 mhz maximum clock frequency ? flexible, uniform erase architecture ? 4-kbyte blocks ? 32-kbyte blocks ? 64-kbyte blocks ? full chip erase ? individual sector protection with global protect/unprotect feature ? sixteen 128-kbyte physical sectors ? hardware controlled locking of protected sectors ? flexible programming ? byte/page program (1 to 256 bytes) ? automatic checking and reporting of erase/program failures ? jedec standard manufacturer and device id read methodology ? low power dissipation ? 7 ma active read current (typical) ? 4 a deep power-down current (typical) ? endurance: 100,000 program/erase cycles ? data retention: 20 years ? complies with full industrial temperature range ? industry standard green (pb/halide-free/rohs compliant) package options ? 8-lead soic (200-mil wide) 1. description the at26df161 is a serial interface flash memory device designed for use in a wide variety of high-volume consumer based applications in which program code is shad- owed from flash memory into embedded or ex ternal ram for execution. the flexible erase architecture of the at26df161, with it s erase granularity as small as 4-kbytes, makes it ideal for data storage as well, eliminating the need for additional data storage eeprom devices. the physical sectoring and the erase block sizes of the at26df161 have been opti- mized to meet the needs of today's code and data storage applications. by optimizing the size of the physical sectors and eras e blocks, the memory space can be used much more efficiently. because certai n code modules and data storage segments must reside by themselves in their own protected sectors, the wasted and unused memory space that occurs with large sectored and large block erase flash memory devices can be greatly reduced. this increa sed memory space effi ciency allows addi- tional code routines and data storage segments to be adde d while still maintaining the same overall device density. 16-megabit 2.7-volt only serial firmware dataflash ? memory at26df161 for new designs use at25df161 3599h?dflash?8/09
2 3599h?dflash?8/09 at26df161 the at26df161 also offers a sophisticated meth od for protecting individual sectors against erroneous or malicious pr ogram and erase operati ons. by providing the ab ility to individually pro- tect and unprotect sectors, a system can unprotect a specific sector to modify its contents while keeping the remaining sectors of the memory array securely protected. this is useful in applica- tions where program code is patched or updated on a subroutine or module basis, or in applications where data storage segments need to be modified without running the risk of errant modifications to the program code segments. in addition to indivi dual sector protection capabili- ties, the at26df161 incorporates global protec t and global unprotect features that allow the entire memory array to be either protected or unprotected all at once. this reduces overhead during the manufacturing process since sectors do not have to be unprotected one-by-one prior to initial programming. specifically designed for use in 3-volt system s, the at26df161 supports read, program, and erase operations with a supply voltag e range of 2.7v to 3.6v. no separate voltage is required for programming and erasing. 2. pin descriptions and pinouts table 2-1. pin descriptions symbol name and function asserted state type cs chip select : asserting the cs pin selects the device. when the cs pin is deasserted, the device will be deselected and normally be placed in standby mode (not deep power-down mode), and the so pin will be in a high-impedance state. when the device is deselected, data will not be accepted on the si pin. a high-to-low transition on the cs pin is required to start an operation, and a low-to-high transition is required to end an operation. when ending an inte rnally self-timed operation such as a program or erase cycle, the device will not enter the st andby mode until the completion of the operation. low input sck serial clock : this pin is used to provide a clock to the device and is used to control the flow of data to and from the device. command, address, and input data present on the si pin is always latched on the rising edge of sck, while output data on the so pin is always clocked out on the falling edge of sck. input si serial input : the si pin is used to shift data into the device. the si pin is used for all data input including command and address sequences. data on the si pin is always latched on the rising edge of sck. input so serial output : the so pin is used to shift data out from the device. data on the so pin is always clocked out on the falling edge of sck. output wp write protect : the wp pin controls the hardware locking fe ature of the device. please refer to ?protection commands and features? on page 11 for more details on pr otection featur es and the wp pin. the wp pin is internally pulled-high and may be left floating if hardware c ontrolled protection will not be used. however, it is recommended that the wp pin also be externally connected to v cc whenever possible. low input v cc device power supply : the v cc pin is used to supply the source voltage to the device. operations at invalid v cc voltages may produce spurious results and should not be attempted. power gnd ground : the ground reference for the power supply. gnd should be connected to the system ground. power
3 3599h?dflash?8/09 at26df161 3. block diagram 4. memory array to provide the gr eatest flexibility, the memory array of th e at26df161 can be erased in four lev- els of granularity including a full chip erase. in addition, the array has been divided into physical sectors of uniform size, of which each sector can be individually protected from program and erase operations. the size of the physical sectors is optimized for both code and data storage applications, allowing both code and data segments to reside in their own isolated regions. figure 4-1 on page 4 illustrates the breakdow n of each erase level as well as the break- down of each physical sector. figure 2-1. 8-soic top view 1 2 3 4 8 7 6 5 cs so wp gnd vcc nc sck si flash memory array y-gating cs sck so si y-decoder address latch x-decoder i/o buffers and latches control and protection logic sram data buffer wp interface control and logic
4 3599h?dflash?8/09 at26df161 figure 4-1. memory architecture diagram internal sectoring for 64kb 32kb 4kb 1-256 byte sector protection block erase block erase block erase page program function (d8h command) (52h command) (20h command) (02h command) 4kb 1fffffh ? 1ff000h 256 bytes 1fffffh ? 1fff00h 256 bytes 1ffeffh ? 1ffe00h 256 bytes 1ffdffh ? 1ffd00h 4kb 1f8fffh ? 1f8000h 256 bytes 1ffcffh ? 1ffc00h 4kb 1f7fffh ? 1f7000h 256 bytes 1ffbffh ? 1ffb00h 256 bytes 1ffaffh ? 1ffa00h 256 bytes 1ff9ffh ? 1ff900h 4kb 1f0fffh ? 1f0000h 256 bytes 1ff8ffh ? 1ff800h 4kb 1effffh ? 1ef000h 256 bytes 1ff7ffh ? 1ff700h 256 bytes 1ff6ffh ? 1ff600h 256 bytes 1ff5ffh ? 1ff500h 4kb 1e8fffh ? 1e8000h 256 bytes 1ff4ffh ? 1ff400h 4kb 1e7fffh ? 1e7000h 256 bytes 1ff3ffh ? 1ff300h 256 bytes 1ff2ffh ? 1ff200h 256 bytes 1ff1ffh ? 1ff100h 4kb 1e0fffh ? 1e0000h 256 bytes 1ff0ffh ? 1ff000h 4kb 1dffffh ? 1df000h 256 bytes 1fefffh ? 1fef00h 256 bytes 1feeffh ? 1fee00h 256 bytes 1fedffh ? 1fed00h 4kb 1d8fffh ? 1d8000h 256 bytes 1fecffh ? 1fec00h 4kb 1d7fffh ? 1d7000h 256 bytes 1febffh ? 1feb00h 256 bytes 1feaffh ? 1fea00h 256 bytes 1fe9ffh ? 1fe900h 4kb 1d0fffh ? 1d0000h 256 bytes 1fe8ffh ? 1fe800h 4kb 1cffffh ? 1cf000h 4kb 1c8fffh ? 1c8000h 256 bytes 0017ffh ? 001700h 4kb 1c7fffh ? 1c7000h 256 bytes 0016ffh ? 001600h 256 bytes 0015ffh ? 001500h 256 bytes 0014ffh ? 001400h 4kb 1c0fffh ? 1c0000h 256 bytes 0013ffh ? 001300h 256 bytes 0012ffh ? 001200h 256 bytes 0011ffh ? 001100h 256 bytes 0010ffh ? 001000h 4kb 01ffffh ? 01f000h 256 bytes 000fffh ? 000f00h 256 bytes 000effh ? 000e00h 256 bytes 000dffh ? 000d00h 4kb 018fffh ? 018000h 256 bytes 000cffh ? 000c00h 4kb 017fffh ? 017000h 256 bytes 000bffh ? 000b00h 256 bytes 000affh ? 000a00h 256 bytes 0009ffh ? 000900h 4kb 010fffh ? 010000h 256 bytes 0008ffh ? 000800h 4kb 00ffffh ? 00f000h 256 bytes 0007ffh ? 000700h 256 bytes 0006ffh ? 000600h 256 bytes 0005ffh ? 000500h 4kb 008fffh ? 008000h 256 bytes 0004ffh ? 000400h 4kb 007fffh ? 007000h 256 bytes 0003ffh ? 000300h 256 bytes 0002ffh ? 000200h 256 bytes 0001ffh ? 000100h 4kb 000fffh ? 000000h 256 bytes 0000ffh ? 000000h 128kb (sector 15) block erase detail 128kb (sector 0) ? ? ? 128kb (sector 14) 64kb page program detail page address block address range ? ? ? ? ? ? range ? ? ? 64kb 64kb 64kb 64kb ? ? ? 32kb 32kb 32kb 32kb ? ? ? ? ? ? ? ? ? 64kb 32kb 32kb 32kb 32kb 32kb ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 32kb 32kb 32kb ? ? ? ? ? ? ? ? ? ? ? ?
5 3599h?dflash?8/09 at26df161 5. device operation the at26df161 is controlled by a set of instructions that are sent from a host controller, com- monly referred to as the spi master. the spi master communicates with the at26df161 via the spi bus which is comprised of four signal lines: chip select (cs ), serial clock (sck), serial input (si), and serial output (so). the spi protocol defines a total of four modes of operation (mode 0, 1, 2, or 3) with each mode differing in respect to the sck polarity and phase and how the polarity and phase control the flow of data on the spi bus. the at26df161 supports the two most common modes, spi modes 0 and 3. the only difference between spi modes 0 and 3 is the polarity of the sck signal when in the inactive state (when the spi master is in standby mode and not transferring any data). with spi modes 0 and 3, data is always latched in on the rising edge of sck and always output on the falling edge of sck. figure 5-1. spi mode 0 and 3 6. commands and addressing a valid instruction or operat ion must always be started by first asserting the cs pin. after the cs pin has been asserted, the spi master must th en clock out a valid 8-bit opcode on the spi bus. following the opcode, instruction dependent info rmation such as addre ss and data bytes would then be clocked out by the spi master. all opcode, address, and data bytes are transferred with the most significant bit (msb) first. an operation is ended by deasserting the cs pin. opcodes not supported by the at26df161 will be ignored by th e device and no operation will be started. the device will continue to ignore any data pr esented on the si pin until the start of the next operation (cs pin being deasserted and then reasserted). in addition, if the cs pin is deas- serted before complete opcode and address information is sent to the device, then no operation will be performed and the device will simply retu rn to the idle state and wait for the next operation. addressing of the device requires a total of th ree bytes of information to be sent, representing address bits a23-a0. since the upper address limit of the at26df161 memory array is 1fffffh, address bits a23-a21 are always ignored by the device. sck cs si so msb lsb msb lsb
6 3599h?dflash?8/09 at26df161 table 6-1. command listing command opcode address bytes dummy bytes data bytes read commands read array 0bh 0000 1011 3 1 1+ read array (low frequency) 03h 0000 0011 3 0 1+ program and erase commands block erase (4-kbytes) 20h 0010 0000 3 0 0 block erase (32-kbytes) 52h 0101 0010 3 0 0 block erase (64-kbytes) d8h 1101 1000 3 0 0 chip erase 60h 0110 0000 0 0 0 c7h 1100 0111 0 0 0 byte/page program (1 to 256 bytes) 02h 0000 0010 3 0 1+ protection commands write enable 06h 0000 0110 0 0 0 write disable 04h 0000 0100 0 0 0 protect sector 36h 0011 0110 3 0 0 unprotect sector 39h 0011 1001 3 0 0 global protect/unprotect use wr ite status register command read sector protection registers 3ch 0011 1100 3 0 1+ status register commands read status register 05h 0000 0101 0 0 1+ write status register 01h 0000 0001 0 0 1 miscellaneous commands read manufacturer and device id 9fh 1001 1111 0 0 1 to 4 deep power-down b9h 1011 1001 0 0 0 resume from deep power-down abh 1010 1011 0 0 0
7 3599h?dflash?8/09 at26df161 7. read commands 7.1 read array the read array command can be used to sequentia lly read a continuous stream of data from the device by simply providi ng the sck signal once the initial starting address has been speci- fied. the device incorporates an internal addres s counter that automatically increments on every clock cycle. two opcodes, 0bh and 03h, can be used for the re ad array command. the use of each opcode depends on the maximum sck frequency that will be used to read data from the device. the 0bh opcode can be used at any sck frequency up to the maximum specified by f sck . the 03h opcode can be used for lower frequency read operations up to the maximum specified by f rdlf . to perform the read array operation, the cs pin must first be asserted and the appropriate opcode (0bh or 03h) must be clocked into the device. after the opcode has been clocked in, the three address bytes must be clocke d in to specify the starting address location of the first byte to read within the memory array. if the 0bh opcode is used, then one don?t care byte must also be clocked in after the three address bytes. after the three address bytes (and the one don?t care byte if using opcode 0bh) have been clocked in, additional clock cycles will result in se rial data being output on the so pin. the data is always output with the msb of a byte first. wh en the last byte (1fffffh) of the memory array has been read, the device will cont inue reading back at the beginn ing of the array (000000h). no delays will be incurred when wrapping around from the end of the array to the beginning of the array. deasserting the cs pin will terminate the read operation and put the so pin into a high-imped- ance state. the cs pin can be deasserted at any time and does not require that a full byte of data be read. figure 7-1. read array ? 0bh opcode figure 7-2. read array ? 03h opcode sck cs si so msb msb 23 1 0 00001011 67 5 41011 9 812 394243 41 40 37 38 33 36 35 34 31 32 29 30 44 47 48 46 45 opcode aaaa aaa a a msb xxxxxxx x msb msb ddddddd d d d address bits a23-a0 don't care data byte 1 high-impedance sck cs si so msb msb 23 1 0 00000011 67 5 41011 9 812 3738 33 36 35 34 31 32 29 30 39 40 opcode aaaa aaa a a msb msb ddddddd d d d address bits a23-a0 data byte 1 high-impedance
8 3599h?dflash?8/09 at26df161 8. program and erase commands 8.1 byte/page program the byte/page program command allows anywhere from a single byte of data to 256 bytes of data to be programmed into previously erased memory locations. an erased memory location is one that has all eight bits set to the logical ?1? state (a byte value of ffh). before a byte/page program command can be started, the write enable command must have been previously issued to the device (see write enable comma nd description) to set the write enable latch (wel) bit of the status register to a logical ?1? state. to perform a byte/page program command, an opcode of 02h must be clocked into the device followed by the three address bytes denoting the first byte location of the memory array to begin programming at. after the address bytes have been clocked in, data can then be clocked into the device and will be stored in an intern al buffer. if the starting memory address denoted by a23-a0 does not fall on an even 256-byte page boundary (a7-a0 are not all 0), then special ci rcumstances regarding which memory locations will be programmed will apply. in this situation, any data that is sent to the device that goes beyond the end of the page will wrap around back to the beginning of the sa me page. for exam- ple, if the starting address denoted by a23-a0 is 0000feh, and three bytes of data are sent to the device, then the first two bytes of data will be prog rammed at addres ses 0000feh and 0000ffh while the last byte of data will be programmed at address 000000h. the remaining bytes in the page (addresses 000001h through 0000fdh) will be unaffected and will not change. in addition, if more than 256 bytes of data are sent to the device, then only the last 256 bytes sent will be latched into the internal buffer. when the cs pin is deasserted, the devi ce will take the data stored in the internal buffer and pro- gram it into the appropriate memory array loca tions based on the starting address specified by a23-a0 and the number of complete data bytes sent to the device. if less than 256 bytes of data were sent to the device, then the remaining bytes within the page will not be altered. the pro- gramming of the data bytes is internally self -timed and should take place in a time of t pp . the three address bytes and at least one complete byte of data must be clocked into the device before the cs pin is deasserted; otherwise, the device will abort the operation and no data will be programmed into the memory array. in addition , if the address specified by a23-a0 points to a memory location within a sector that is in the protected state (see ?protect sector? on page 12 ), then the byte/page program command will not be executed, and the dev ice will return to the idle state once the cs pin has been deasserted. the wel bit in the status register will be reset back to the logical ?0? state if the program cycle aborts due to an incomp lete address being sent, an incomplete byte of data being sent, or be cause the memory location to be programmed is protected. while the device is programming, the status r egister can be read and will indicate that the device is busy. for faster throughput, it is recommended that the status register be polled rather than waiting the t pp time to determine if the data bytes have finished programming. at some point before the pr ogram cycle completes, the wel bit in the status register will be reset back to the logical ?0? state. the device also incorporates an intelligent prog ramming algorithm that can detect when a byte location fails to program correc tly. if a programming error arises, it will be indicated by the epe bit in the status register.
9 3599h?dflash?8/09 at26df161 figure 8-1. byte program figure 8-2. page program 8.2 block erase a block of 4k-, 32k-, or 64k-bytes can be erased (a ll bits set to the logical ?1? state) in a single operation by using one of three different opcodes for the block erase command. an opcode of 20h is used for a 4k-byte erase, an opcode of 52h is used for a 32k-byt e erase, and an opcode of d8h is used for a 64k-byte erase. before a block erase command can be started, the write enable command must have been previously issued to the device to set the wel bit of the sta- tus register to a logical ?1? state. to perform a block erase, the cs pin must first be asserted and the appropriate opcode (20h, 52h, or d8h) must be clocked into the device. after the opcode has been clocked in, the three address bytes specifying an address within the 4k -, 32k-, or 64k-byte block to be erased must be clocked in. any additional data clocked into the device will be ignored. when the cs pin is deasserted, the device will erase the appropriate block. the er asing of the block is internally self-timed and should take place in a time of t blke . since the block erase command erases a region of bytes, the lower order address bits do not need to be decoded by the device. therefore, for a 4k-byte erase, address bits a11-a0 will be ignored by the device and their values can be ei ther a logical ?1? or ?0?. for a 32k-byte erase, address bits a14-a0 will be igno red, and for a 64k-byte erase, address bits a15-a0 will be ignored by the device. despite the lower order address bits not being decoded by the device, the complete three address bytes must still be clocked into the device before the cs pin is deas- serted; otherwise, the device will abort the operation and no erase operati on will be performed. sck cs si so msb msb 23 1 0 00000010 67 5 41011 9 812 39 37 38 33 36 35 34 31 32 29 30 opcode high-impedance aaaa aaa a a msb ddddddd d address bits a23-a0 data in sck cs si so msb msb 23 1 0 00000010 67 5 49 839 37 38 33 36 35 34 31 32 29 30 opcode high-impedance aa aaa a msb ddddddd d address bits a23-a0 data in byte 1 msb ddddddd d data in byte n
10 3599h?dflash?8/09 at26df161 if the address specified by a23-a0 points to a me mory location within a sector that is in the pro- tected state, then the block erase command will not be executed, and the device will return to the idle state once the cs pin has been deasserted. the wel bit in the status register will be reset back to the logical ?0? state if the erase cycle aborts due to an incomplete address being sent or because a memory location within the region to be erased is protected. while the device is executing a successful erase cycle, the status regist er can be read and will indicate that the device is busy. for faster throughput, it is recommended that the status regis- ter be polled rather than waiting the t blke time to determine if the dev ice has finished erasing. at some point before the erase cycle completes, the wel bit in the status register will be reset back to the logical ?0? state. the device also incorporates an intelligent erasing algorithm that can detect when a byte loca- tion fails to erase properly. if an erase error occurs, it will be indicated by the epe bit in the status register. figure 8-3. block erase 8.3 chip erase the entire memory array can be erased in a si ngle operation by using the chip erase command. before a chip erase command can be started, the write enable command must have been pre- viously issued to the device to set the wel bit of the status register to a logical ?1? state. two opcodes, 60h and c7h, can be used for the chip erase command. there is no difference in device functionality when utilizin g the two opcodes, so they c an be used interchangeably. to perform a chip erase, one of the two opcodes (60h or c7h) must be clocked into the device. since the entire memory array is to be erased, no address bytes need to be clocked into the device, and any data clocked in after the opcode will be i gnored. when the cs pin is deasserted, the device will erase the entire memory array. the erasing of the device is internally self-timed and should take place in a time of t chpe . the complete opcode must be clock ed into the device before the cs pin is deasserted; other- wise, no erase will be performed. in addition, if any sector of the memory array is in the protected state, then the chip erase command will not be executed , and the device will return to the idle state once the cs pin has been deasserted. the wel bit in the status register will be reset back to the logical ?0? state if a sector is in the protected state. while the device is executing a successful erase cycle, the status regist er can be read and will indicate that the device is busy. for faster throughput, it is recommended that the status regis- ter be polled rather than waiting the t chpe time to determine if the de vice has finished erasing. at sck cs si so msb msb 23 1 0 cccccccc 67 5 41011 9 812 31 29 30 27 28 26 opcode aaaa aaa a a a a a address bits a23-a0 high-impedance
11 3599h?dflash?8/09 at26df161 some point before the erase cycle completes, the wel bit in the status register will be reset back to the logical ?0? state. the device also incorporates an intelligent erasing algorithm that can detect when a byte loca- tion fails to erase properly. if an erase error occurs, it will be indicated by the epe bit in the status register. figure 8-4. chip erase 9. protection commands and features 9.1 write enable the write enable command is used to set the writ e enable latch (wel) bit in the status regis- ter to a logical ?1? state. the wel bit must be set before a program, erase, protect sector, unprotect sector, or write stat us register command can be exec uted. this makes the issuance of these commands a two step process, ther eby reducing the chances of a command being accidentally or erroneously executed. if the wel bi t in the status register is not set prior to the issuance of one of thes e commands, then the comma nd will not be executed. to issue the write enable command, the cs pin must first be asserted and the opcode of 06h must be clocked into the device. no address by tes need to be clocked into the device, and any data clocked in afte r the opcode will be ig nored. when the cs pin is deasserted, the wel bit in the status register will be set to a logical ?1 ?. the complete opcode must be clocked into the device before the cs pin is deasserted; otherwise, the device will abort the operation and the state of the wel bit will not change. figure 9-1. write enable sck cs si so msb 23 1 0 cccccccc 67 5 4 opcode high-impedance sck cs si so msb 23 1 0 00000110 67 5 4 opcode high-impedance
12 3599h?dflash?8/09 at26df161 9.2 write disable the write disable command is used to reset the write enable latch (wel) bit in the status reg- ister to the logical ?0? state. with the wel bit re set, all program, erase, protect sector, unprotect sector, and write status regi ster commands will not be execut ed. the write disable command is also used to exit the sequential program mo de. other conditions can also cause the wel bit to be reset; for more details, refer to the wel bi t section of the status register description on page 21 . to issue the write disable command, the cs pin must first be asserted and the opcode of 04h must be clocked into the device. no address by tes need to be clocked into the device, and any data clocked in afte r the opcode will be ig nored. when the cs pin is deasserted, the wel bit in the status register will be reset to a logical ?0 ?. the complete opcode mu st be clocked into the device before the cs pin is deasserted; otherwise, the device will abort the operation and the state of the wel bit will not change. figure 9-2. write disable 9.3 protect sector every physical sector of the devi ce has a corresponding single-bit sector protection register that is used to control the so ftware protection of a sector. up on device power-up or after a device reset, each sector protec tion register will default to the logi cal ?1? state indicating that all sectors are protected and cannot be programmed or erased. issuing the protect sector co mmand to a particular sector add ress will set the corresponding sector protection register to the logical ?1? st ate. the following table out lines the two states of the sector protection registers. before the protect sector command can be issued, the write enable command must have been previously issued to set the wel bi t in the status register to a lo gical ?1?. to issue the protect sector command, the cs pin must first be asserted and the opcode of 36h must be clocked into the device followed by three address bytes designating any address within the sector to be locked. any additional data clocked into the device will be ignored. when the cs pin is deas- serted, the sector protection register corresponding to the physical sector addressed by a23- a0 will be set to the logical ?1? state, and the sector itself will then be protected from program sck cs si so msb 23 1 0 00000100 67 5 4 opcode high-impedance table 9-1. sector protection register values value sector protection status 0 sector is unprotected and ca n be programmed and erased. 1 sector is protected and cannot be programm ed or erased. this is the default state.
13 3599h?dflash?8/09 at26df161 and erase operations. in addition , the wel bit in the status regi ster will be reset back to the log- ical ?0? state. the complete three address bytes must be clocked into the device before the cs pin is deas- serted; otherwise, the device will abort the operation, the state of the sector protection register will be unchanged, and the wel bi t in the status register w ill be reset to a logical ?0?. as a safeguard against accidental or erroneous protecting or unprotecting of sectors, the sector protection registers can themselves be locked fr om updates by using the sprl (sector protec- tion registers locked) bit of the st atus register (please refer to ?status register commands? on page 19 for more details). if the sector protection registers are locked, then any attempts to issue the protect sector command will be ignored, and the device will reset the wel bit in the status register back to a logical ?0? and return to the idle state once the cs pin has been deasserted. figure 9-3. protect sector 9.4 unprotect sector issuing the unprotect sector co mmand to a particular sector ad dress will reset the correspond- ing sector protection register to the logical ?0? state (see table 9-1 on page 12 for sector protection register values). every physical sector of the device has a corresponding single-bit sector protection register that is used to control the software protection of a sector. before the unprotect sector command can be issued, the write enable command must have been previously issued to set the wel bit in the status register to a logical ?1?. to issue the unprotect sector command, the cs pin must first be asserted and the opcode of 39h must be clocked into the device. after the opcode has been clocked in, the three address bytes designat- ing any address within the sector to be unlocked must be clocked in. any additional data clocked into the device after the address bytes will be ignored. when the cs pin is deasserted, the sec- tor protection register corresponding to the sector addressed by a23-a0 will be reset to the logical ?0? state, and the sector itself will be unprotected. in addition, the wel bit in the status register will be reset back to the logical ?0? state. the complete three address bytes must be clocked into the device before the cs pin is deas- serted; otherwise, the device will abort the operation, the state of the sector protection register will be unchanged, and the wel bi t in the status register w ill be reset to a logical ?0?. as a safeguard against accidental or erroneous locking or unlocking of sectors, the sector pro- tection registers can themselves be locked from updates by using the sprl (sector protection registers locked) bit of the status register (please refer to ?status register commands? on page 19 for more details). if the sector protection registers are locked, then any attempts to sck cs si so msb msb 23 1 0 00110110 67 5 41011 9 812 31 29 30 27 28 26 opcode aaaa aaa a a a a a address bits a23-a0 high-impedance
14 3599h?dflash?8/09 at26df161 issue the unprotect sect or command will be ignore d, and the device will re set the wel bit in the status register back to a logical ?0? and return to the idle state once the cs pin has been deasserted. figure 9-4. unprotect sector 9.5 global protect/unprotect the global protect and global un protect features can work in co njunction with the protect sec- tor and unprotect sector functions. for exampl e, a system can globally protect the entire memory array and then use the unprotect sector command to individually unprotect certain sec- tors and individually reprotect t hem later by using the protec t sector command. likewise, a system can globally unprotect the entire memory array and then individually protect certain sec- tors as needed. performing a global protect or global unprotec t is accomplished by writing a certain combina- tion of data to the status regist er using the write status regi ster command (see ?write status register? section on page 21 for command execution details). the write status register com- mand is also used to modify the sprl (sector protection registers lo cked) bit to control hardware and software locking. to perform a global protect, the appropriate wp pin and sprl conditions must be met and the system must write a logical ?1? to bits 5, 4, 3, and 2 of the status register. conversely, to per- form a global unprotect, the same wp and sprl conditions must be met but the system must write a logical ?0? to bits 5, 4, 3, and 2 of the status register. table 9-2 details the conditions necessary for a global protect or global unprotect to be performed. sck cs si so msb msb 23 1 0 00111001 67 5 41011 9 812 31 29 30 27 28 26 opcode aaaa aaa a a a a a address bits a23-a0 high-impedance
15 3599h?dflash?8/09 at26df161 essentially, if the sprl bit of the status register is in the logical ?0? state (sector protection registers are not locked), then wr iting a 00h to the status regi ster will perform a global unpro- tect without changing the state of the sprl bit. similarly, writing a 7fh to the status register will perform a global protect and keep the sprl bit in the logical ?0? state. the sprl bit can, of course, be changed to a logical ?1? by writing an ffh if software-locking or hardware-locking is desired along with the global protect. table 9-2. valid sprl and global prot ect/unprotect conditions wp state current sprl value new write status register data protection operation new sprl value bit 7 6 5 4 3 2 1 0 00 0 x 0 0 0 0 x x 0 x 0 0 0 1 x x 0 x 1 1 1 0 x x 0 x 1 1 1 1 x x 1 x 0 0 0 0 x x 1 x 0 0 0 1 x x 1 x 1 1 1 0 x x 1 x 1 1 1 1 x x global unprotect ? all sector protection registers reset to 0 no change to current protection. no change to current protection. no change to current protection. global protect ? all sector protection registers set to 1 global unprotect ? all sector protection registers reset to 0 no change to current protection. no change to current protection. no change to current protection. global protect ? all sector protection registers set to 1 0 0 0 0 0 1 1 1 1 1 0 1 x x x x x x x x no change to the current protection level. all sectors currently protected will remain protected and all sectors currently unprotected will remain unprotected. the sector protection registers are hard-locked and cannot be changed when the wp pin is low and the current state of sprl is 1. therefore, a global protect/unprotect will not occur. in addition, the sprl bit cannot be changed (the wp pin must be high in order to change sprl back to a 0). 10 0 x 0 0 0 0 x x 0 x 0 0 0 1 x x 0 x 1 1 1 0 x x 0 x 1 1 1 1 x x 1 x 0 0 0 0 x x 1 x 0 0 0 1 x x 1 x 1 1 1 0 x x 1 x 1 1 1 1 x x global unprotect ? all sector protection registers reset to 0 no change to current protection. no change to current protection. no change to current protection. global protect ? all sector protection registers set to 1 global unprotect ? all sector protection registers reset to 0 no change to current protection. no change to current protection. no change to current protection. global protect ? all sector protection registers set to 1 0 0 0 0 0 1 1 1 1 1 11 0 x 0 0 0 0 x x 0 x 0 0 0 1 x x 0 x 1 1 1 0 x x 0 x 1 1 1 1 x x 1 x 0 0 0 0 x x 1 x 0 0 0 1 x x 1 x 1 1 1 0 x x 1 x 1 1 1 1 x x no change to the current protection level. all sectors currently protected will remain protected, and all sectors currently unprotected will remain unprotected. the sector protection registers are soft-locked and cannot be changed when the current state of sprl is 1. therefore, a global protect/unprotect will not occur. however, the sprl bit can be changed back to a 0 from a 1 since the wp pin is high. to perform a global protect/unprotect, the write status register command must be issued again after the sprl bit has been changed from a 1 to a 0. 0 0 0 0 0 1 1 1 1 1
16 3599h?dflash?8/09 at26df161 if the desire is to only change the sprl bit wi thout performing a global protect or global unpro- tect, then the system can simply write a 0fh to the status register to change the sprl bit from a logical ?1? to a logical ?0? provided the wp pin is deasserted. likewi se, the system can write an f0h to change the sprl bit from a logical ?0? to a logical ?1? without affecting the current sector protection status (no chang es will be made to the sect or protection registers). when writing to the status register, bits 5, 4, 3, and 2 will not actually be modified but will be decoded by the device for the pur poses of the global protect and global unprotect functions. only bit 7, the sprl bit, will actually be modified. therefore, when readin g the status register, bits 5, 4, 3, and 2 will not reflect the values wri tten to them but will instead indicate the status of the wp pin and the sector protection status. please refer to the ?read status register? section and table 10-1 on page 19 for details on the status register format and what values can be read for bits 5, 4, 3, and 2. 9.6 read sector pr otection registers the sector protection regi sters can be read to determine the current software protection status of each sector. reading the se ctor protection registers, how ever, will not determine the status of the wp pin. to read the sector protection regist er for a particular sector, the cs pin must first be asserted and the opcode of 3ch must be clocked in. once the opcode has been clocked in, three address bytes designating any address withi n the sector must be clocked in. after the last address byte has been clocked in, the device will begin output ting data on the so pin during every subse- quent clock cycle. the data being output will be a repeating byte of either ffh or 00h to denote the value of the appropriate sector protection register deasserting the cs pin will terminate the read operation and put the so pin into a high-imped- ance state. the cs pin can be deasserted at any time and does not require that a full byte of data be read. in addition to reading the individual sector pr otection registers, the software protection status (swp) bit in the status register can be read to determine if all, some, or none of the sectors are software protected (please refer to ?status register commands? on page 19 for more details). table 9-3. read sector protection register ? output data output data sector protection register value 00h sector protection register valu e is 0 (sector is unprotected). ffh sector protection register value is 1 (sector is protected).
17 3599h?dflash?8/09 at26df161 figure 9-5. read sector protection register 9.7 protected states and the write protect (wp ) pin the wp pin is not linked to the memory array itself and has no direct effect on the protection sta- tus of the memory array. instead, the wp pin, in conjunction with the sprl (sector protection registers locked) bit in the status register, is used to control the hardware locking mechanism of the device. for hardware locking to be active, two conditions must be met ? the wp pin must be asserted and the sprl bit must be in the logical ?1? state. when hardware locking is active, the sector protection registers are locked and the sprl bit itself is also locked. therefore, sectors that are protected will be locked in the protected state, and sectors that are unpr otected will be locked in the unprotected state. these states cannot be changed as long as hardware locking is active, so the protect sector, unprotect sector, and write status register commands will be ignored. in order to modi fy the protection status of a sector, the wp pin must first be deasserted, and the sprl bit in the status register must be reset back to the logical ?0? state using the writ e status register command. when resetting the sprl bit back to a logical ?0?, it is not possible to perform a global protect or global unprotect at the same time since the sect or protection registers remain soft-locked until after the write status register command has been executed. if the wp pin is permanently connected to gnd, then once the sprl bit is set to a logical ?1?, the only way to reset the bit back to the logical ?0? state is to power-cycle or reset the device. this allows a system to power-up with all sect ors software protected but not hardware locked. therefore, sectors can be unprotected and protec ted as needed and then hardware locked at a later time by simply setting the sprl bit in the status register. when the wp pin is deasserted, or if the wp pin is permanently connected to v cc , the sprl bit in the status regist er can still be set to a logical ?1? to lo ck the sector protec tion registers. this provides a software locking ability to prevent erro neous protect sector or unprotect sector com- mands from being processed. when changing the sprl bit to a logical ?1? from a logical ?0?, it is also possible to perform a global protect or global unprotect at the same time by writing the appropriate values into bits 5, 4, 3, and 2 of the status register. sck cs si so msb msb 23 1 0 00111100 67 5 41011 9 812 3738 33 36 35 34 31 32 29 30 39 40 opcode aaaa aaa a a msb msb ddddddd d d d address bits a23-a0 data byte high-impedance
18 3599h?dflash?8/09 at26df161 the tables below detail the various protec tion and locking states of the device. note: 1. ?n? represents a sector number table 9-4. software protection register states wp sector protection register n (1) sector n (1) x (don't care) 0 unprotected 1protected table 9-5. hardware and software locking wp sprl locking sprl change allowed sector protection registers 0 0 can be modified from 0 to 1 unlocked and modifiable using the protect and unprotect sector commands. global protect and unprotect can also be performed. 01 hardware locked locked locked in current state. protect and unprotect sector commands will be ignored. global protect and unprotect cannot be performed. 1 0 can be modified from 0 to 1 unlocked and modifiable using the protect and unprotect sector commands. global protect and unprotect can also be performed. 11 software locked can be modified from 1 to 0 locked in current state. protect and unprotect sector commands will be ignored. global protect and unprotect cannot be performed.
19 3599h?dflash?8/09 at26df161 10. status register commands 10.1 read status register the status register can be read to determine the device?s ready/ busy status, as well as the sta- tus of many other functions such as hardware locking and software protection. the status register can be read at any ti me, including during an internally self-timed program or erase operation. to read the status register, the cs pin must first be asserted and the opcode of 05h must be clocked into the device. after t he last bit of the opcode has b een clocked in, the device will begin outputting status register data on the so pin during every subsequent clock cycle. after the last bit (bit 0) of the status regi ster has been clocked out, the se quence will repeat itself starting again with bit 7 as long as the cs pin remains asserted and the sck pin is being pulsed. the data in the status regi ster is constantly be ing updated, so each repe ating sequence will output new data. deasserting the cs pin will terminate the read status register operation and put the so pin into a high-impedance state. the cs pin can be deasserted at any time and does not require that a full byte of data be read. notes: 1. only bit 7 of the status register will be mo dified when using the write status register command. 2. r/w = readable and writeable r = readable only table 10-1. status register format bit (1) name type (2) description 7 sprl sector protection registers locked r/w 0 sector protection regist ers are unlocked (default). 1 sector protection registers are locked. 6 res reserved for future use r 0 reserved for future use. 5 epe erase/program error r 0 erase or program operation was successful. 1 erase or program error detected. 4 wpp write protect (wp ) pin status r 0wp is asserted. 1wp is deasserted. 3:2 swp software protection status r 00 all sectors are software unprotected (all sector protection registers are 0). 01 some sectors are software protected. read individual sector protection registers to determine which sectors are protected. 10 reserved for future use. 11 all sectors are software protected (all sector protection registers are 1 ? default). 1 wel write enable latch status r 0 device is not write enabled (default). 1 device is write enabled. 0 rdy/bs y ready/busy status r 0 device is ready. 1 device is busy with an internal operation.
20 3599h?dflash?8/09 at26df161 10.1.1 sprl bit the sprl bit is used to control whether the sect or protection registers can be modified or not. when the sprl bit is in the logical ?1? state, all sector protection registers are locked and can- not be modified with the protect sector and un protect sector commands (the device will ignore these commands). in addition, the global protect and global u nprotect features cannot be per- formed. any sectors that are presently pr otected will remain protected, and any sectors that are presently unprot ected will remain unprotected. when the sprl bit is in the logi cal ?0? state, all sector prot ection registers are unlocked and can be modified (the protect sect or and unprotect sector command s, as well as the global pro- tect and global unprotect features, will be processed as normal). the sprl bit defaults to the logical ?0? state after a power-up or a device reset. the sprl bit can be modified freely whenever the wp pin is deasserted. however, if the wp pin is asserted, then the sprl bit may only be changed from a logical ?0? (sector protection regis- ters are unlocked) to a logical ?1? (sector protec tion registers are locked). in order to reset the sprl bit back to a logical ?0? using the write status register command, the wp pin will have to first be deasserted. the sprl bit is the only bit of the status regist er that can be user modified via the write status register command. 10.1.2 epe bit the epe bit indicates whether the last erase or program operation completed successfully or not. if at least one byte during the erase or program operation did not erase or program properly, then the epe bit will be set to the logical ?1? state. the epe bit will not be set if an erase or pro- gram operation aborts for any reason such as an attempt to erase or program a protected region or if the wel bit is not set prior to an erase or program operation. the epe bit will be updated after every erase and program operation. 10.1.3 wpp bit the wpp bit can be read to determine if the wp pin has been asserted or not. 10.1.4 swp bits the swp bits provide feedback on the software pr otection status for the device. there are three possible combinations of the swp bits that indicate whether none, some, or all of the sectors have been protected using the protect sector co mmand or the global protect feature. if the swp bits indicate that some of the sectors ha ve been protected, then t he individual sector pro- tection registers can be read with the read sect or protection register s command to determine which sectors are in fact protected.
21 3599h?dflash?8/09 at26df161 10.1.5 wel bit the wel bit indicates the current status of the internal write enable latch. when the wel bit is in the logical ?0? state, the device will not accept any program, erase, pr otect sector, unprotect sector, or write status register commands. the wel bit defaults to the logical ?0? state after a device power-up or reset. in addi tion, the wel bit will be reset to the logical ?0? state automati- cally under the following conditions: ? write disable operation completes successfully ? write status register operatio n completes successfully or aborts ? protect sector operation co mpletes successfully or aborts ? unprotect sector operation comp letes successfully or aborts ? byte/page program operation completes successfully or aborts ? block erase operation completes successfully or aborts ? chip erase operation completes successfully or aborts if the wel bit is in the logical ?1? state, it will not be reset to a logical ?0? if an operation aborts due to an incomplete or unrecognized opcode being clocked into the device before the cs pin is deasserted. in order for the wel bit to be reset when an operation aborts prematurely, the entire opcode for a program, erase, protect sector, unpr otect sector, or write status register com- mand must have been clocked into the device. 10.1.6 rdy/bsy bit the rdy/bsy bit is used to determi ne whether or not an internal operation, such as a program or erase, is in progress. to po ll the rdy/bsy bit to detect the co mpletion of a pr ogram or erase cycle, new status register data must be contin ually clocked out of the device until the state of the rdy/bsy bit changes from a logical ?1? to a logical ?0?. figure 10-1. read status register 10.2 write status register the write status register command is used to modify the sprl bit of the status register and/or to perform a global protect or global un protect operation. before the write status regis- ter command can be issued, the write enable co mmand must have been previously issued to set the wel bit in the status register to a logical ?1?. to issue the write status register command, the cs pin must first be asserted and the opcode of 01h must be clocked into th e device followed by one byte of data. the one byte of data con- sists of the sprl bit value, a don't care bit, f our data bits to denote whether a global protect or sck cs si so msb 23 1 0 00000101 67 5 41011 9 812 2122 17 20 19 18 15 16 13 14 23 24 opcode msb msb dddddd d d d d msb ddddd d d d status register data status register data high-impedance
22 3599h?dflash?8/09 at26df161 unprotect should be performed, and tw o additional don?t care bits (see table 10-2 ). any addi- tional data bytes that ar e sent to the device will be ignored. when the cs pin is deasserted, the sprl bit in the status register will be modified and the wel bit in the status register will be reset back to a logical ?0?. the values of bits 5, 4, 3, and 2 and the state of the sprl bit before the write status regist er command was executed (the prior stat e of the sprl bit) will determine whether or not a global protect or global unprotect will be pe rfomed. please refe r to the ?global protect/unprotect? section on page 14 for more details. the complete one byte of data must be clocked into the device before the cs pin is deasserted; otherwise, the device will abort the operation, the st ate of the sprl bit will not change, no potential global protect or unprotect will be performed, and the wel bit in the status register will be reset back to the logical ?0? state. if the wp pin is asserted, then the sprl bit can only be set to a logical ?1?. if an attempt is made to reset the sprl bit to a logical ?0? while the wp pin is asserted, then the write status register command will be ignored, a nd the wel bit in the status regist er will be reset back to the logical ?0? state. in order to reset the sprl bit to a logical ?0?, the wp pin must be deasserted. figure 10-2. write status register table 10-2. write status register format bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 sprl x global protect/unprotect x x sck cs si so msb 23 1 0 0000000 67 5 41011 9 81415 13 12 opcode msb 1dxddddx x status register in high-impedance
23 3599h?dflash?8/09 at26df161 11. other commands and functions 11.1 read manufacturer and device id identification information can be read from the dev ice to enable systems to electronically query and identify the device while it is in system. the identificati on method and the command opcode comply with the jedec standard for ?manufacturer and device id read methodology for spi compatible serial interf ace memory devices?. the type of information that can be read from the device includes the jedec defined manufacturer id, the vendor specific device id, and the ven- dor specific extended device information. to read the identification information, the cs pin must first be asserted and the opcode of 9fh must be clocked into the device. after the opc ode has been clocked in, the device will begin out- putting the identification data on the so pin during the subsequent cloc k cycles. the first byte that will be output will be the manufacturer id followed by two bytes of device id information. the fourth byte output will be the extended device in formation stri ng length, which will be 00h indicating that no extended device information fo llows. after the extend ed device information string length byte is output, the so pin will go into a high-i mpedance state; ther efore, additional clock cycles will have no affect on the so pi n and no data will be output. as indicated in the jedec standard, reading the extended device information string length and any subsequent data is optional. deasserting the cs pin will terminate the manufacturer and device id read operation and put the so pin into a high-i mpedance state. the cs pin can be deasserted at any time and does not require that a full byte of data be read. table 11-1. manufacturer and devi ce id information byte no. data type value 1 manufacturer id 1fh 2 device id (part 1) 46h 3 device id (part 2) 00h 4 extended device information string length 00h table 11-2. manufacturer and de vice id details data type bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 hex value details manufacturer id jedec assigned code 1fh jedec code: 0001 1111 (1fh for atmel) 00011111 device id (part 1) family code density code 46h family code: density code: 010 (at26dfxxx series) 00110 (16-mbit) 01000110 device id (part 2) mlc code product version code 00h mlc code: product version: 000 (1-bit/cell technology) 00000 (initial version) 00000000
24 3599h?dflash?8/09 at26df161 figure 11-1. read manufacturer and device id 11.2 deep power-down during normal operation, the device will be placed in the standby mode to consume less power as long as the cs pin remains deasserted and no internal operation is in progress. the deep power-down command offers the ab ility to place the device into an even lower power consump- tion state called the deep power-down mode. when the device is in the deep power-down mode, all commands including the read status register command will be ignored with the e xception of the resume from deep power-down command. since all commands will be ignored, the mode can be used as an extra protection mechanism against program and erase operations. entering the deep power-down mode is accomplished by simply asserting the cs pin, clocking in the opcode of b9h, and then deasserting the cs pin. any additional data clocked into the device after the opcode will be igno red. when the cs pin is deasserted, the device will enter the deep power-down mode within the maximum time of t edpd . the complete opcode must be clocked in before the cs pin is deasserted; otherwise, the device will abort the operation and return to the standby mode once the cs pin is deasserted. in addi- tion, the device will default to the standby mode after a po wer-cycle or a device reset. the deep power-down command will be ignored if an internally self-timed operation such as a program or erase cycle is in progress. the deep power-down command must be reissued after the internally self-timed operation has been comp leted in order for the device to enter the deep power-down mode. sck cs si so 6 0 9fh 8 7 38 opcode 1fh 46h 00h 00h manufacturer id device id byte 1 device id byte 2 extended device information string length high-impedance 14 16 15 22 24 23 30 32 31 note: each transition shown for si and so represents one byte (8 bits)
25 3599h?dflash?8/09 at26df161 figure 11-2. deep power-down 11.3 resume from deep power-down in order exit the deep power-down mode and re sume normal device operation, the resume from deep power-down command must be issu ed. the resume from deep power-down com- mand is the only command that the device will re cognize while in the d eep power-down mode. to resume from the deep power-down mode, the cs pin must first be asserted and opcode of abh must be clocked into the device. any addi tional data clocked into the device after the opcode will be ignored. when the cs pin is deasserted, the devic e will exit the deep power- down mode within the maximum time of t rdpd and return to the standby mode. after the device has returned to the standby mode, normal command operations such as read array can be resumed. if the complete opcode is not clocked in before the cs pin is deasserted, then the device will abort the operation and return to the deep power-down mode. figure 11-3. resume from deep power-down sck cs si so msb i cc 23 1 0 10111001 67 5 4 opcode high-impedance standby mode current active current deep power-down mode current t edpd sck cs si so msb i cc 23 1 0 10101011 67 5 4 opcode high-impedance deep power-down mode current active current standby mode current t rdpd
26 3599h?dflash?8/09 at26df161 12. electrical specifications 12.1 absolute maximum ratings* temperature under bias.... .............. ........... .....-55 ? c to +125 ? c *notice: stresses beyond those listed under ?absolute maximum ratings? may cause permanent dam- age to the device. this is a stress rating only and functional operation of t he device at these or any other conditions beyond those indicated in the operational sections of this specification is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. storage temperature .......................................-65 ? c to +150 ? c all input voltages (including nc pins) with respect to ground .....................................-0.6v to +4.1v all output voltages with respect to ground .............................-0.6v to v cc + 0.5v 12.2 dc and ac operating range at26df161 operating temperat ure (case) ind. -40 ? c to +85 ? c v cc power supply 2.7v to 3.6v 12.3 dc characteristics symbol parameter condition min typ max units i sb standby current cs , wp = v cc , all inputs at cmos levels 25 35 a i dpd deep power-down current cs , wp = vcc, all inputs at cmos levels 48a i cc1 active current, read operation f = 66 mhz, i out = 0 ma, cs = v il , v cc = max 11 15 ma f = 50 mhz; i out = 0 ma, cs = v il , v cc = max 10 14 f = 33 mhz, i out = 0 ma, cs = v il , v cc = max 812 f = 20 mhz, i out = 0 ma, cs = v il , v cc = max 710 i cc2 active current, program operation cs = v cc , v cc = max 12 18 ma i cc3 active current, erase operation cs = v cc , v cc = max 14 20 ma i li input leakage current v in = cmos levels 1 a i lo output leakage current v out = cmos levels 1 a v il input low voltage 0.3 x v cc v v ih input high voltage 0.7 x v cc v v ol output low voltage i ol = 1.6 ma, v cc = min 0.4 v v oh output high voltage i oh = -100 a v cc - 0.2 v
27 3599h?dflash?8/09 at26df161 notes: 1. not 100% tested (value guaranteed by design and characterization). 2. only applicable as a constraint for the write status register command when sprl = 1. notes: 1. not 100% tested (value guaranteed by design and characterization). 12.4 ac characteristics symbol parameter min max units f sck serial clock (sck) frequency 66 mhz f rdlf sck frequency for read array (low frequency ? 03h opcode) 33 mhz t sckh sck high time 6.8 ns t sckl sck low time 6.8 ns t sckr (1) sck rise time, peak-to-peak (slew rate) 0.1 v/ns t sckf (1) sck fall time, peak-to-peak (slew rate) 0.1 v/ns t csh chip select high time 50 ns t csls chip select low setup time (relative to sck) 5 ns t cslh chip select low hold time (relative to sck) 5 ns t cshs chip select high setup ti me (relative to sck) 5 ns t cshh chip select high hold time (relative to sck) 5 ns t ds data in setup time 2 ns t dh data in hold time 3 ns t dis (1) output disable time 6ns t v output valid time 6ns t oh output hold time 0 ns t wps (1)(2) write protect setup time 20 ns t wph (1)(2) write protect hold time 100 ns t secp (1) sector protect time (from chip select high) 20 ns t secup (1) sector unprotect time (from chip select high) 20 ns t edpd (1) chip select high to deep power-down 3 s t rdpd (1) chip select high to standby mode 3 s 12.5 program and er ase characteristics symbol parameter min typ max units t pp page program time (256 bytes) 1.5 5.0 ms t blke block erase time 4-kbyte 0.05 0.2 sec 32-kbyte 0.35 0.6 64-kbyte 0.7 1.0 t chpe (1) chip erase time 18 28 sec t wrsr (1) write status register time 200 ns
28 3599h?dflash?8/09 at26df161 12.7 input test waveforms and measurement levels 12.8 output test load 12.6 power-up conditions parameter min max units minimum v cc to chip select low time 50 s power-up device delay before program or erase allowed 10 ms power-on reset voltage 1.5 2.5 v ac driving levels ac measurement level 0.45v 1.5v 2.4v t r , t f < 2 ns (10% to 90%) device under test 30 pf
29 3599h?dflash?8/09 at26df161 13. ac waveforms figure 13-1. serial input timing figure 13-2. serial output timing figure 13-3. wp timing for write status register command when sprl = 1 cs si sck so msb high-impedance msb lsb t csls t sckh t sckl t cshs t cshh t ds t dh t cslh t csh cs si sck so t v t sckh t sckl t dis t v t oh wp si sck so 00 0 high-impedance msb x t wps t wph cs lsb of write status register data byte msb of write status register opcode msb of next opcode
30 3599h?dflash?8/09 at26df161 14. ordering information 14.1 green package options (pb/ halide-free/rohs compliant) f sck (mhz) ordering code package operation range 66 AT26DF161-SU 8s2 industrial (-40c to +85c) package type 8s2 8-lead, 0.209" wide, plastic gull wing small outline package (eiaj soic)
31 3599h?dflash?8/09 at26df161 15. packaging information 15.1 8s2 ? eiaj soic title drawing no. gpc rev. package drawing contact: packagedrawings@atmel.com 8s2 stn f 8s2, 8-lead, 0.208? body, plastic small outline package (eiaj) 4/15/08 common dimensions (unit of measure = mm) symbol min nom max note notes: 1. this drawing is for general information only; refer to eiaj drawing edr-7320 for additional information. 2. mismatch of the upper and lower dies and resin burrs aren't included. 3. determines the true geometric position. 4. values b,c apply to plated terminal. the standard thickness of the plating layer shall measure between 0.007 to .021 mm. a 1.70 2.16 a1 0.05 0.25 b 0.35 0.48 4 c 0.15 0.35 4 d 5.13 5.35 e1 5.18 5.40 2 e 7.70 8.26 l 0.51 0.85 0 8 e 1.27 bsc 3 1 1 n n e e top view t o p v i e w c c e1 e 1 end view e n d v i e w a a b b l l a1 a 1 e e d d side view s i d e v i e w
32 3599h?dflash?8/09 at26df161 16. revision history revision level ? release date history a ? november 2005 initial release b ? march 2006 added global protect and global unprotect feature - made various minor text changes throughout document - added global protect/unprotect section to document - changed write status register section changed ?power-up device delay before pr ogram or erase allowed? specification - reduced from 20 ms maximum to 10 ms maximum c ? april 2006 changed note 5 of 8s2 package drawing to generalize terminal plating comment d ? may 2006 removed ?preliminary? designation changed page program specification in section 12.5 - increased maximum page progra m time from 3.0 ms to 5.0 ms added footnote (1) to t chpe parameter in section 12.5 e ? july 2006 added errata regarding chip erase. f ? september 2006 added epe bit description to the read status register section. added references to th e epe bit throughout text. g ? august 2008 removed 8m1-a package offering. h ? august 2009 added ?for new designs use at25df161? reference on front page
33 3599h?dflash?8/09 at26df161 17. errata 17.1 chip erase 17.1.1 issue in a certain percentage of units, the chip er ase feature may not function correctly and may adversely affect device operation. therefore, it is recommended that the chip erase commands (opcodes 60h and c7h) not be used. 17.1.2 workaround use the block erase (4kb, 32kb, or 64kb) comma nds as an alternative. the block erase func- tion is not affected by the chip erase issue. 17.1.3 resolution the chip erase feature is being fixed with a new revision of the device. please contact atmel for the estimated availability of devices with the fix.
3599h?dflash?8/09 headquarters international atmel corporation 2325 orchard parkway san jose, ca 95131 usa tel: 1(408) 441-0311 fax: 1(408) 487-2600 atmel asia room 1219 chinachem golden plaza 77 mody road tsimshatsui east kowloon hong kong tel: (852) 2721-9778 fax: (852) 2722-1369 atmel europe le krebs 8, rue jean-pierre timbaud bp 309 78054 saint-quentin-en- yvelines cedex france tel: (33) 1-30-60-70-00 fax: (33) 1-30-60-71-11 atmel japan 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel: (81) 3-3523-3551 fax: (81) 3-3523-7581 product contact web site www.atmel.com technical support dataflash@atmel.com sales contact www.atmel.com/contacts literature requests www.atmel.com/literature disclaimer: the information in this document is provided in connection wi th atmel products. no license, expr ess or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of atmel products. except as set forth in atmel?s terms and condi- tions of sale located on atmel?s web site, atmel assumes no li ability whatsoever and disclaims any express, implied or statutor y warranty relating to its products including , but not limited to, the implied warranty of merchantability, fitness for a particu lar purpose, or non-infringement. in no event shall atmel be liable for any direct, indire ct, consequential, punitive, special or i nciden- tal damages (including, without li mitation, damages for loss of profits, business interruption, or loss of information) arising out of the use or inability to use this document, even if atmel has been advised of the possibility of such damages. atmel makes no representations or warranties with respect to the accuracy or comp leteness of the contents of th is document and reserves the rig ht to make changes to specifications and product descriptions at any time without notice. atmel does not make any commitment to update the information contained her ein. unless specifically provided otherwise, atmel products are not suitable for, and shall not be used in, automotive applications. atmel?s products are not int ended, authorized, or warranted for use as components in applications intended to support or sustain life. ? 2009 atmel corporation . all rights reserved. atmel ? , atmel logo and combinations thereof, everywhere you are ? , dataflash ? and others, are registered trademarks or trademarks of atmel corporatio n or its subsidiaries. other terms and product names may be trademar ks of others.

▲Up To Search▲

Price & Availability of AT26DF161-SU

	To Download AT26DF161-SU Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .